You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The current naming convention for Chef sample apps is to use a hash which is generated by digesting the metadata information of the sample app. The initial idea was that it would be advantageous to relate the meta info to the hash to help identify the app and associate it with the config. This turns out not to be useful if the config files undergo frequent changes due to tooling changes like zapp updates or name changes within the spec.
There was no value added by using the complex meta file digestion to name the sample apps. It would be better to remove it and encourage the naming convention to be applied only upon creation of new sample apps. I.e. the naming convention should not be applied to previously created apps so we can maintain consistency for CI/CD testing pipelines.
@gautesl did you work on the Sphinx documentation in #24185 ? If so, would you know why the CI test here is failing?
Hi, an update to the doc dependancy pydata-sphinx-theme broke the build. A fix for it is suggested here #25893, and further doc issues preventing a successful build are proposed here #25894
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The current naming convention for Chef sample apps is to use a hash which is generated by digesting the metadata information of the sample app. The initial idea was that it would be advantageous to relate the meta info to the hash to help identify the app and associate it with the config. This turns out not to be useful if the config files undergo frequent changes due to tooling changes like zapp updates or name changes within the spec.
There was no value added by using the complex meta file digestion to name the sample apps. It would be better to remove it and encourage the naming convention to be applied only upon creation of new sample apps. I.e. the naming convention should not be applied to previously created apps so we can maintain consistency for CI/CD testing pipelines.