dell/terraform-provider-redfish

Terraform provider for Redfish REST APIs

terraform-provider-redfish's Issues

FIX- Linting issue of power resource with golangci-lint configuration change

FIX- Linting issue of power resource with golangci-lint configuration change

Originally posted by @Krishnan-Priyanshu in #105 (comment)

QUESTION: Pulumi bridge ?

Hello,

I was wondering if you would consider bridging the terraform provider to Pulumi?

You only have one repository to maintain (this one) and the bridge will be easily updated (there are probably a way to automate that)
Take a look at the official documentation from pulumi for that : https://github.com/pulumi/pulumi-tf-provider-boilerplate 👍

BIOS update is not idempotent

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform CLI and Terraform Redfish Provider Version

terraform -v
Terraform v0.14.7

Server(s) details and firmware version

PowerEdge R640
iDRAC 9 version 4.20.20.20

Affected Resource(s)

redfish_bios

Terraform Configuration Files

# Copy-paste your Terraform configurations here - for large Terraform configs,
# please use a service like Dropbox and share a link to the ZIP file.
resource "redfish_bios" "bios" {

  redfish_server {
    endpoint = "https://192.168.8.103:6443"
    ssl_insecure = true
  }
  attributes = {
    "SysProfile" = "PerfOptimized"
  }
  settings_apply_time = "OnReset"
  action_after_apply = "ForceRestart"
}

Debug Output

https://gist.github.com/brutus333/950a67e89c0a099356060af3a4ea4f2e

Panic Output

Expected Behavior

Once the configuration is updated TF should not try to change the resource again

Actual Behavior

Terraform tried to update the resource again (even if it was compliant with the definition), so the change is not idempotent as it should be.

Steps to Reproduce

1. terraform apply

Important Factoids

References

• #0000

BUG - File names must be consistent across the provider

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Issues

For some reason two of the files in the redfish folder are not compliant with the convention resource_redfish_XXXXXX. These are:

• resource_simple_update.go
• resource_user_account.go

Need to change for:

• resource_redfish_simple_update.go
• resource_redfish_user_account.go

TODO: resource_redfish_storage_volume enhancements

Just leaving here this issue to keep track of enhancements that need to be done in the resource_redfish_storage_volume resource.

Comments

• Always Immediate operations are preferred.
• This resource has not have implemented the read or update function since we cannot update a volume. To "update it" in some way, we would need to destroy and the recreate it. I think that's not a desired behavior here.

Things to do

• The validate function for settingsApplyTime needs to be implemented.

• Better handling on OnReset operations. If a job is created using terraform, and then the server is restarted manually, the new volume will be there (if the job was successful). At this point, if a terraform destroy command is issued, it will look for the new volume and destroy it rightaway, without creating a job (this scenario might be buggy for controllers that does not support Immediate opperations).

• Since the iDRAC still doesn't support DELETE operation on standard tasks collection, tasks cannot be deleted in a standard way for all vendors. Here I had to implement the propietary way iDRAC manages jobs (/redfish/v1/Managers/iDRAC.Embedded.1/Jobs/) through the redfish API. This will change in the future as soon as iDRAC redfish implementation supports that, Function to do this is common.DeleteDellJob

Darwin support

Please add support for macOS (darwin) builds and releases. It is super inconvenient to use a local build.

NEW FEATURE: Add resource and data source for Boot Order

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

• Add a new redfish provider resource for server boot option configuration. It should be able to support the following features:
  • Enable, disable or continue boot override
  • set one-time boot
  • set persistent boot order
  • set default boot order
• Add a new redfish provider data source for retrieving the boot order and boot options details.

New or Affected Resource(s)

• resource_redfish_system_boot
• data_source_redfish_system_boot

Potential Terraform Configuration

# Copy-paste your Terraform configurations here - for large Terraform configs,
# please use a service like Dropbox and share a link to the ZIP file.

References

• #0000

NEW FEATURE: GitHub actions to create binaries when versions are tagged

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

As soon as new versions of this provider are tagged, we need to kick off a pipeline that eventually compile the provider (for windows, linux and darwing) and publish it within the packages section.

Also this is a requirement for publishing provider binaries to the terraform registry:
https://www.terraform.io/docs/registry/providers/publishing.html#github-actions-preferred-

Tasks

• Copy the GoReleaser configuration from the terraform-provider-scaffolding repository to the root of your repository.
• Copy the GitHub Actions workflow from the terraform-provider-scaffolding repository to .github/workflows/release.yml in your repository.

These actions above are only the ones regarding this repo. To fully integrate with the terraform registry, all of them must be followed:
https://www.terraform.io/docs/registry/providers/publishing.html#github-actions-preferred-

NEW FEATURE: Datasource for Storage Volume

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

Create a new datasource for getting the different storage from the Redfish API as well as all its different volumes attached to it.

New or Affected Resource(s)

New datasource

• redfish_storage_volume

Potential Terraform Configuration

provider "redfish" {}

data "redfish_storage_volume" "storage" {
    for_each = var.rack1

    redfish_server {
        user = each.value.user
        password = each.value.password
        endpoint = each.value.endpoint
        ssl_insecure = each.value.ssl_insecure
    }      
}

References

Unit test cases for Bios resource

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

Unit test cases for Bios resource

New or Affected Resource(s)

• resource_redfish_bios

Potential Terraform Configuration

# Copy-paste your Terraform configurations here - for large Terraform configs,
# please use a service like Dropbox and share a link to the ZIP file.

References

• #0000

Update gofish dependency to v0.11.0

Current master code does not compile because gofish library dependency is set to use v0.10.0 instead of v0.11.0.
This prevents the plugins system to work.

Wait for BIOS update job to finish

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

While updating BIOS setup using this provider I noticed that it created a job on the iDRAC but it did not wait for the job to finish.
IMHO the correct behavior (from TF perspective) it is to wait (sync or async) for the resource configuration to be applied.
The code can be changed to use existing method WaitForJobToFinish

New or Affected Resource(s)

• redfish_bios

Potential Terraform Configuration

# Copy-paste your Terraform configurations here - for large Terraform configs,
# please use a service like Dropbox and share a link to the ZIP file.
resource "redfish_bios" "bios" {

  redfish_server {
    endpoint = "https://192.168.8.103:6443"
    ssl_insecure = true
  }
  attributes = {
    "SysProfile" = "PerfOptimized"
  }
  settings_apply_time = "OnReset"
  action_after_apply = "ForceRestart"
  wait_to_finish = true
}

References

• #0000

DOCUMENTATION: Add documentation for redfish provider resources and data sources

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

Add provider documentation inline with Terraform guidelines using tfplugindocstool to automatically generate documentation for redfish provider in the format required by the Terraform Registry. The plugin will read the descriptions and schema of each resource and data source in redfish provider and generate the relevant Markdown files. For more details see https://learn.hashicorp.com/tutorials/terraform/provider-release-publish.

New or Affected Resource(s)

• all redfish provider resources

References

• #0000

NEW FEATURE: Add resource for computer system reset

Description

Add a new Redfish provider resource for computer system reset. It should be able to support all the reset type operations supported by a server for e.g. On, Off, GracefulRestart, GracefulShutdown, ForceOff, ForceRestart etc.

New or Affected Resource(s)

new resource

Potential Terraform Configuration

# Copy-paste your Terraform configurations here - for large Terraform configs,
# please use a service like Dropbox and share a link to the ZIP file.

References

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

NEW FEATURE: resource_user_account acceptance tests

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

New acceptance tests for resource_user_account

New or Affected Resource(s)

• resource_user_account

Potential Terraform Configuration

# Copy-paste your Terraform configurations here - for large Terraform configs,
# please use a service like Dropbox and share a link to the ZIP file.

Boot once form virtual dvd

How should we go about booting form virtual dvd once?

resource "redfish_boot_source_override" "boot" {
  for_each = var.rack1

  redfish_server {
    user         = each.value.user
    password     = each.value.password
    endpoint     = each.value.endpoint
    ssl_insecure = each.value.ssl_insecure
  }

  // boot source override parameters
  boot_source_override_enabled = "Once"
  boot_source_override_target  = "UefiTarget"
    
  boot_source_override_mode    = "UEFI"

  // Reset parameters to be applied after bios settings are applied
  reset_type    = "ForceRestart"
  reset_timeout = "120"
  # // The maximum amount of time to wait for the bios job to be completed
  boot_source_job_timeout = "1200"
  depends_on = [ redfish_virtual_media.vm ]
}

NEW FEATURE: Add resource for manager reset

Description

Add a new Redfish provider resource for manager reset. It should support all the reset type operations that is supported by a BMC for e.g. GracefulRestart, ForceRestart etc.

New or Affected Resource(s)

New resource

Potential Terraform Configuration

# Copy-paste your Terraform configurations here - for large Terraform configs,
# please use a service like Dropbox and share a link to the ZIP file.

References

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Should getSystemResource() be in some sort of common file?

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

I'm working on #15. In resource_redfish_bios.go I see that there is a function getSystemResource which resolves an instance of GoFish's service to a concrete system which I figure will be reused across multiple modules. I tried asking on StackOverflow to see if there is a good way to handle functionality shared across different resources. It would seem Go doesn't have stylistic guidance on the subject.

Right now my code is referencing getSystemResource in resource_redfish_bios.go which I figure is undesirable. Is there a preferred way to handle this scenario?

Consider splitting out gofish/dell into its own repository

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

Is there any intention of splitting out the Gofish Dell 'plugin' into its own repository?

https://github.com/dell/terraform-provider-redfish/tree/master/gofish/dell

I'm mainly asking since I'd like to import the Gofish Dell 'plugin' in another non-terraform project and possibly implement 'plugins' for other vendors.

References

• #0000

Feat: Add the possibility to choose the system to interact with

Hello,

I currently have a dell xr4000. I would like to be able to configure my RAID disks with redfish using the provider. However, I have two systems in the /redfish/v1/Systems directory. These are my main node (XR4510c) and the witness server (XR4000w). However, the terraform provider doesn't allow me to choose which system I want to interact with. It will therefore default to the XR4000w, which has no RAID card...

Thanks in advance for your help.

NEW FEATURE - Implement Lock to avoid asynchronous operations to collide

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

When dealing with this provider, resources need to be aware of other resources, because when performing configurations, server reboots might be needed.
This causes race conditions if several resources creation are run concurrently.

To avoid this, and also to avoid the depends_on tag (Terraform recommends to use this as last resort), Hashicorp suggested to implement a global Lock used by resources when it comes to configuring a server. This will make aware one resource of the creation of other one.

New or Affected Resource(s)

• redfish_user_account
• redfish_bios
• redfish_storage_volume
• redfish_virtual_media
• redfish_power
• redfish_simple_update

Tasks

• Implement Lock in a separate package
• Declare the Lock as a global variable in provider.go
• Use the Lock in redfish_user_account resource
• Use the Lock in redfish_bios resource
• Use the Lock in redfish_storage_volume resource
• Use the Lock in redfish_virtual_media resource
• Use the Lock in redfish_power resource
• Use the Lock in redfish_simple_update resource

References

• #0000

Unit test cases for power control

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

Unit test case for power control

New or Affected Resource(s)

• resource_redfish_power.go

You can assign @grantcurell

NEW FEATURE: Add support for expanding the Boot Options for Boot data source

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

Add support for expanding the Boot Options for Boot data source. The data source should also provide a list of the boot options and their details, similar to the following:

$ curl -k -s https://192.168.10.10/redfish/v1/Systems/System.Embedded.1/BootOptions/Boot0001 | python -m json.tool
{
    "@odata.context": "/redfish/v1/$metadata#BootOption.BootOption",
    "@odata.id": "/redfish/v1/Systems/System.Embedded.1/BootOptions/Boot0001",
    "@odata.type": "#BootOption.v1_0_3.BootOption",
    "BootOptionEnabled": true,
    "BootOptionReference": "Boot0001",
    "Description": "Current settings of the UEFI Boot option",
    "DisplayName": "PXE Device 2: Integrated NIC 1 Port 1 Partition 1",
    "Id": "Boot0001",
    "Name": "Uefi Boot Option",
    "UefiDevicePath": "VenHw(D227C733-F75F-4341-B749-4D1759EC8538)"
}

New or Affected Resource(s)

• data_source_redfish_boot

Potential Terraform Configuration

# Copy-paste your Terraform configurations here - for large Terraform configs,
# please use a service like Dropbox and share a link to the ZIP file.

References

• #0000

NEW FEATURE: Add Virtual Media resource and datasource

This issue is to keep track of the implementation of VirtualMedia resource and datasource.

• Resource: The user must be able to mount and unmount ISOs place on HTTP, CIFS or NFS shares.

• Datasource: The user must be able to check the different virtual medias that can be used in the resource.

• VirtualMedia resource implementation.

• VirtualMedia datasource implementation.

Github actions for publishing provider on Terraform registry

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

In order to publish this provider to Terraform registry, some requisites need to be met according this: Publishing Providers.

Task list:

• Create and export a signing key that you plan on using to sign your provider releases. See Preparing and Adding a Signing Key for more information
• Copy the GoReleaser configuration from the terraform-provider-scaffolding repository to the root of your repository.
• Copy the GitHub Actions workflow from the terraform-provider-scaffolding repository to .github/workflows/release.yml in your repository.
• Go to Settings > Secrets in your repository, and add the following secrets:
  -- GPG_PRIVATE_KEY - Your ASCII-armored GPG private key. You can export this with gpg --armor --export-secret-keys [key ID or email].
  -- PASSPHRASE - The passphrase for your GPG private key.
• Push a new valid version tag (e.g. v1.2.3) to test that the GitHub Actions releaser is working.

NEW FEATURE: Implement SimpleUpdate on the provider

• - Write CRUD Operations that carries out the expected behavior ( Update the firmware of the machine)
• - Create unit tests for the code written

Feature Request: Allow the configuration of a hotspare

Currently, the redfish_storage_volume allows the creation of a virtual disk on a redfish endpoint. However, there is no way to assign a physical drive to become either a global hotspare or a virtual drive hotspare.

Thanks in advance for your time to evaluate this feature request.

Add Makefile

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

Add a makefile for building the provider binary and copying it to the default user plugin location.

New or Affected Resource(s)

None

Potential Terraform Configuration

Should be able to build the binary for all OS_ARCH and copy them to the default plugin path.

# build 
$ make build

# install
$ make install

References

• #0000

Remove datasource and resource provider configuration

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

As of now the provider is using provider configuration as part of datasource and resource attributes to circumvent one endpoint per provider limitation.
However, a more Terraform like solution would rely on multiple providers and provider aliases: Terraform supports what is called multiple provider configuration via aliases: https://www.terraform.io/docs/language/providers/configuration.html#alias-multiple-provider-configurations

Terraform code will not look very nice since will be some repetition in the provider definition code but it will be more likely that the provider itself will continue to work. However, there are open issues on terraform project dealing with usage of for_each and count for providers code so probably there will be a fix in the near future.
For provider code duplication issue there are some other solutions like terragrunt.

New or Affected Resource(s)

All datasources and resources are affected by this change

Potential Terraform Configuration

provider "redfish" {
    user = "john"
    password = "password"
    endpoint = "http://172.17.0.2"
    ssl_insecure = true
    alias = "bios1"
}
provider "redfish" {
    user = "john"
    password = "password"
    endpoint = "http://172.17.0.3"
    ssl_insecure = true
    alias = "bios2"
}

data "redfish_bios" "bios_1" {
  provider = redfish.bios1
}

data "redfish_bios" "bios_2" {
  provider = redfish.bios2
}

References

• #0000

Aditional comments

I already fixed the code to allow this, if you find it valuable I can make a PR.

I have to say that the provider code is simplified by using this pattern.

data - redfish_dell_idrac_attributes - "unexpected end of JSON input"

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform CLI and Terraform Redfish Provider Version

Terraform Cloud Workspace Version 1.7.0
Redfish Provider Version 1.1.0

Server(s) details and firmware version

Dell R930 (D8KQRD2)

iDRAC 8
BIOS Version 2.13.0
Firmware Version 2.85.85.85

Affected Resource(s)

data "redfish_dell_idrac_attributes"

Terraform Configuration Files

terraform {
  required_providers {
    redfish = {
      source = "dell/redfish"
      version = "1.1.0"
    }
  }
}

provider "redfish" {
    user = var.idrac_username
    password = var.idrac_password
}

data "redfish_dell_idrac_attributes" "idrac" {
  redfish_server {
    endpoint      = var.r930_idrac_endpoint
    ssl_insecure = true
  }
}

data "redfish_bios" "bios" {
  redfish_server {
    endpoint      = var.r930_idrac_endpoint
    ssl_insecure = true
  }
}

variable "idrac_username" {
  type = string
  sensitive = true
}

variable "idrac_password" {
  type = string
  sensitive = true
}

variable "r930_idrac_endpoint" {
  type = string
  sensitive = true
}

Debug Output

https://gist.github.com/robbycuenot/b1db72eb7a2e2d167498abe2ab140fe7

Panic Output

None

Expected Behavior

The data block should have been read and added to the state, as the BIOS attributes did.

Actual Behavior

After ~10 seconds, an unexpected EOF is received and the iDRAC attributes are not imported to the state

Steps to Reproduce

1. terraform apply

Important Factoids

Running on terraform cloud, using a local linux agent with the official TFC container from here: https://hub.docker.com/r/hashicorp/tfc-agent/tags

Other resources work correctly, such as creating user accounts or retrieving BIOS attributes.

It is possible that this is a timeout issue, as the iDRACs tend to have slow response times.

References

QUESTION: Kickstart/cloud-init provisioning

Hi! What's the recommended way to install OS and make the initial configuration with this provider?
Looks like there is no way to pass kickstart or cloud-init files directly from the terraform.
Is the integration with user_data possible?
Or should I host a PXE server for this?

NEW FEATURE: Add resource for manager attributes configuration

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

Create a new Redfish resource for provisioning manager attributes.

New or Affected Resource(s)

new resource

Potential Terraform Configuration

An example terraform plan for manager attribute configuration could be:

# Copy-paste your Terraform configurations here - for large Terraform configs,
# please use a service like Dropbox and share a link to the ZIP file.

resource "redfish_manager" "manager" {
  for_each = var.rack1

  redfish_server {
    user = each.value.user
    password = each.value.password
    endpoint = each.value.endpoint
    ssl_insecure = each.value.ssl_insecure
  }

  attributes = {
    "SNMPAlert.1.Destination" = "192.168.10.11"
    "SNMPAlert.2.Destination" = "192.168.10.12"
    "SNMPAlert.3.Destination" = "192.168.10.13"
  }
}

References

New release?

When do you plan to release v1,1?