Skip to content
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

MGMT-14704: Provide info on custom/vs non custom manifest in manifest endpoint. #5278

Merged
merged 1 commit into from Jul 3, 2023

Commits on Jul 3, 2023

  1. MGMT-14704: Provide info on custom/vs non custom manifest in manifest…

    … endpoint.
    
    It has been reported that users have no way to determine whether or not a manifest is a custom manifest or one generated by the assisted-service.
    This PR introduces a change that uses the file system to store additional metadata about a manifest to indicate whether or not the manifest is a custom one.
    
    For example, if the original file is stored in
    
    ```
    "e09df13f-6f31-42c2-8361-2b5605f80e77/manifests/openshift/99-openshift-machineconfig-master-kargs.yaml"
    ```
    
    Then, if an only if the manifest is custom -  a corresponding metadata file will be created in the following path.
    
    ```
    "e09df13f-6f31-42c2-8361-2b5605f80e77/manifest-attributes/openshift/99-openshift-machineconfig-master-kargs.yaml/user-defined"
    ```
    
    Any internally generated manifests are considered to be "non custom" and are created as such.
    All other manifests are considered to be custom and will follow the scheme above.
    
    When the user retrieves the manifest list, an additional parameter will be supplied for each manifest to indicate the custom/non custom status of the manifest.
    paul-maidment committed Jul 3, 2023
    Copy the full SHA
    cc79b03 View commit details
    Browse the repository at this point in the history