/AWS1/CL_OWXSOURCE¶
Contains the information required to retrieve an app or cookbook from a repository. For more information, see Creating Apps or Custom Recipes and Cookbooks.
CONSTRUCTOR
¶
IMPORTING¶
Optional arguments:¶
IV_TYPE
TYPE /AWS1/OWXSOURCETYPE
/AWS1/OWXSOURCETYPE
¶
The repository type.
IV_URL
TYPE /AWS1/OWXSTRING
/AWS1/OWXSTRING
¶
The source URL. The following is an example of an Amazon S3 source URL:
https://s3.amazonaws.com/opsworks-demo-bucket/opsworks_cookbook_demo.tar.gz
.
IV_USERNAME
TYPE /AWS1/OWXSTRING
/AWS1/OWXSTRING
¶
This parameter depends on the repository type.
For Amazon S3 bundles, set
Username
to the appropriate IAM access key ID.For HTTP bundles, Git repositories, and Subversion repositories, set
Username
to the user name.
IV_PASSWORD
TYPE /AWS1/OWXSTRING
/AWS1/OWXSTRING
¶
When included in a request, the parameter depends on the repository type.
For Amazon S3 bundles, set
Password
to the appropriate IAM secret access key.For HTTP bundles and Subversion repositories, set
Password
to the password.For more information on how to safely handle IAM credentials, see https://docs.aws.amazon.com/general/latest/gr/aws-access-keys-best-practices.html.
In responses, OpsWorks Stacks returns
*FILTERED***
instead of the actual value.
IV_SSHKEY
TYPE /AWS1/OWXSTRING
/AWS1/OWXSTRING
¶
In requests, the repository's SSH key.
In responses, OpsWorks Stacks returns
*FILTERED***
instead of the actual value.
IV_REVISION
TYPE /AWS1/OWXSTRING
/AWS1/OWXSTRING
¶
The application's version. OpsWorks Stacks enables you to easily deploy new versions of an application. One of the simplest approaches is to have branches or revisions in your repository that represent different versions that can potentially be deployed.
Queryable Attributes¶
Type¶
The repository type.
Accessible with the following methods¶
Method | Description |
---|---|
GET_TYPE() |
Getter for TYPE, with configurable default |
ASK_TYPE() |
Getter for TYPE w/ exceptions if field has no value |
HAS_TYPE() |
Determine if TYPE has a value |
Url¶
The source URL. The following is an example of an Amazon S3 source URL:
https://s3.amazonaws.com/opsworks-demo-bucket/opsworks_cookbook_demo.tar.gz
.
Accessible with the following methods¶
Method | Description |
---|---|
GET_URL() |
Getter for URL, with configurable default |
ASK_URL() |
Getter for URL w/ exceptions if field has no value |
HAS_URL() |
Determine if URL has a value |
Username¶
This parameter depends on the repository type.
For Amazon S3 bundles, set
Username
to the appropriate IAM access key ID.For HTTP bundles, Git repositories, and Subversion repositories, set
Username
to the user name.
Accessible with the following methods¶
Method | Description |
---|---|
GET_USERNAME() |
Getter for USERNAME, with configurable default |
ASK_USERNAME() |
Getter for USERNAME w/ exceptions if field has no value |
HAS_USERNAME() |
Determine if USERNAME has a value |
Password¶
When included in a request, the parameter depends on the repository type.
For Amazon S3 bundles, set
Password
to the appropriate IAM secret access key.For HTTP bundles and Subversion repositories, set
Password
to the password.For more information on how to safely handle IAM credentials, see https://docs.aws.amazon.com/general/latest/gr/aws-access-keys-best-practices.html.
In responses, OpsWorks Stacks returns
*FILTERED***
instead of the actual value.
Accessible with the following methods¶
Method | Description |
---|---|
GET_PASSWORD() |
Getter for PASSWORD, with configurable default |
ASK_PASSWORD() |
Getter for PASSWORD w/ exceptions if field has no value |
HAS_PASSWORD() |
Determine if PASSWORD has a value |
SshKey¶
In requests, the repository's SSH key.
In responses, OpsWorks Stacks returns
*FILTERED***
instead of the actual value.
Accessible with the following methods¶
Method | Description |
---|---|
GET_SSHKEY() |
Getter for SSHKEY, with configurable default |
ASK_SSHKEY() |
Getter for SSHKEY w/ exceptions if field has no value |
HAS_SSHKEY() |
Determine if SSHKEY has a value |
Revision¶
The application's version. OpsWorks Stacks enables you to easily deploy new versions of an application. One of the simplest approaches is to have branches or revisions in your repository that represent different versions that can potentially be deployed.
Accessible with the following methods¶
Method | Description |
---|---|
GET_REVISION() |
Getter for REVISION, with configurable default |
ASK_REVISION() |
Getter for REVISION w/ exceptions if field has no value |
HAS_REVISION() |
Determine if REVISION has a value |