We pulled in the configuration documentation from open source for the new repository prefix field.
We also moved the existing EKS ARN documentation into the required registry secret configuration block to consolidate that information in one place. Do we normally try to keep optional configuration on a multi-purpose top level key in the same section? In this case there are multiple ways now to configure the app registry secret.
We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story.
The labels on this github issue will be updated when the story is started.
We pulled in the configuration documentation from open source for the new repository prefix field.
We also moved the existing EKS ARN documentation into the required registry secret configuration block to consolidate that information in one place. Do we normally try to keep optional configuration on a multi-purpose top level key in the same section? In this case there are multiple ways now to configure the app registry secret.