What would you like to be added:
A feature to exclude files or folders for the OCM "github" access type using a ".ocmignore" file.
Why is this needed:
This approach enables maintaining a single repository for deployments across both public cloud and air-gapped environments.
In the public cloud, SAP handles the deployment, requiring landscape-specific details to be included in the repository.
However, for private cloud (air-gapped) deployments, these landscape-specific details are unnecessary and contain internal information. Sharing such details with customer spaces is not a best practice.
What is the benefit
- Implementing this feature will significantly reduce the operational burden of maintaining separate repositories for private and public cloud deployments.
- allowing us to rely entirely on the GitHub access type.
- Not required to clone the repo locally to change it as type "dir"
- Ensure's only necessary folders/files are shipped to air gapped environment
What would you like to be added:
A feature to exclude files or folders for the OCM "github" access type using a ".ocmignore" file.
Why is this needed:
This approach enables maintaining a single repository for deployments across both public cloud and air-gapped environments.
In the public cloud, SAP handles the deployment, requiring landscape-specific details to be included in the repository.
However, for private cloud (air-gapped) deployments, these landscape-specific details are unnecessary and contain internal information. Sharing such details with customer spaces is not a best practice.
What is the benefit