Skip to content
This repository has been archived by the owner on Mar 24, 2023. It is now read-only.

add the AmazonEKS template function to the amazon_eks and kubectl_apply docs #422

Merged
merged 8 commits into from
Aug 20, 2018
Merged

add the AmazonEKS template function to the amazon_eks and kubectl_apply docs #422

merged 8 commits into from
Aug 20, 2018

Conversation

laverya
Copy link
Member

@laverya laverya commented Aug 20, 2018

What I Did

Updated the docs for the amazon_eks resource and kubectl_apply lifecycle step to include the "AmazonEKS" template function, fulfilling part of #377.
Added an "extended_description" field to mutations.json which is included in the generated docs but not the page title.
Added an integration test for the "AmazonEKS" template function, fulfilling the other part of #377.
Included the "AmazonEKS" template function set (ShipContext) anywhere the InstallationContext set was used.

closes #377.

How I Did it

How to verify it

The integration test runs successfully and renders the path to the kubeconfig within the inline asset.

Description for the Changelog

Picture of a Boat (not required but encouraged)

image

@laverya laverya requested a review from areed August 20, 2018 22:12
@@ -494,6 +494,7 @@
},
"merge": {
"description": "An `amazon_eks` asset generates a terraform file that will create an Amazon EKS Cluster.",
"extended_description": "It also populates a template function `AmazonEKS` that takes the name of the cluster and returns the path to the generated kubeconfig for the cluster. This path is only valid after the `render` and `terraform` lifecycle steps have run. This is intended to be used within the [kubectl_apply](/api/ship-lifecycle/lifecycle/kubectl_apply/) lifecycle step.}}",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why }} at end of line?

@@ -13,6 +13,7 @@
"properties": {
"amazon_eks": {
"description": "An `amazon_eks` asset generates a terraform file that will create an Amazon EKS Cluster.",
"extended_description": "It also populates a template function `AmazonEKS` that takes the name of the cluster and returns the path to the generated kubeconfig for the cluster. This path is only valid after the `render` and `terraform` lifecycle steps have run. This is intended to be used within the [kubectl_apply](/api/ship-lifecycle/lifecycle/kubectl_apply/) lifecycle step.}}",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

here too

@@ -0,0 +1,6 @@
customer_id: "-Am-_6i5pw0u4AbspOwKN4lZUCn49u_G"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you should consider adding new tests to init_app instead of base, since init_app auto-creates the release in the staging env

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fair point, I'll move it

@laverya laverya merged commit 620e7ef into replicatedhq:master Aug 20, 2018
@laverya laverya deleted the update-amazon_eks-docs branch August 20, 2018 23:48
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Integration test and documentation needed for AmazonEKS template function
3 participants