-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[IT-3523] Update Service Catalog AMI testing docs #1306
base: master
Are you sure you want to change the base?
[IT-3523] Update Service Catalog AMI testing docs #1306
Conversation
Document the current manual process used for testing changes to AMIs used by service catalog products.
Update the documentation on how to perform functional and integration testing of AMIs used by service catalog products now that test artifacts are automatically created. Depends on Sage-Bionetworks-IT/packer-ami-template Depends on Sage-Bionetworks-IT/service-catalog-library
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sounds good.
execute the validations by running `pre-commit run --all-files`. | ||
Please install pre-commit, once installed the file validations will | ||
automatically run on every commit. | ||
|
||
### Functional Testing | ||
The process to test the functionality of an AMI and it's integration with our |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it's -> its
account, allowing anyone with write access to the packer repos to create test | ||
AMIs, and anyone with write access to service-catalog-library to upload test | ||
templates for service catalog to S3. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
all bullets are '1', below
product template to S3, and create a new Service Catalog product in the | ||
scipool dev account to verify manually from https://sc-dev.sageit.org/ | ||
|
||
The deploy pipelines for both our packer repos and our service catalog library |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you link to the "packer repo's"?
templates for service catalog to S3. | ||
|
||
1. Commit changes to the packer repo to update or modify the AMI on a branch | ||
that starts with `test/`, and push directly to the origin repo. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"to the origin repo'" -> "to the origin branch".
Can you please link the words "the packer repo" to the packer repo' URL?
1. Manually create an EC2 instance in the `itsandbox` account from the test AMI | ||
for any initial system validation, then terminate it. | ||
1. Commit changes to `service-catalog-library` on a branch that starts with | ||
`test/` to update the desired template, and push directly to the origin repo. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
to the origin branch
1. Commit changes to `service-catalog-library` on a branch that starts with | ||
`test/` to update the desired template, and push directly to the origin repo. | ||
1. Create a pull request for `organizations-infra` to add a new Service Catalog | ||
product to `scipool-dev` with 'test' in the name for the test template. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you mention where the "product" templates are located in the repo'? How does the product reference the template in the previous step?
execute the validations by running `pre-commit run --all-files`. | ||
Please install pre-commit, once installed the file validations will | ||
automatically run on every commit. | ||
|
||
### Functional Testing | ||
The process to test the functionality of an AMI and it's integration with our | ||
Service Catalog products is to first create a test AMI, upload a modified |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Below you say to create the new product via a PR, not by uploading to S3. Can you please be consistent?
Update the documentation on Service Catalog integration testing to reflect new automation added to the process.