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
Right now the /scripts folder in the repo contains
a lot of different scripts and it's not clear what users should expect to find in this directory
scripts that are not used from our CI
We should re-organise the structure of this directory. For example we have scripts for deploying in airgap, gathering images from a bundle, and scripts for fetching bundle versions #1035
the logical grouping of the script that gets all images + its supporting files (e.g. requirements.txt) should be placed in a path where it is obvious that it contains these sort of scripts. As a developer, I won't expect the fetch image scripts to be placed all around in scripts/ and in airgap/.
The suggestion we are making is to have all the scripts and supporting files in the same directory as we strive for correctness and a more logical grouping.
Bug Description
This was created after the discussion in #1038 (comment)
Right now the
/scripts
folder in the repo containsWe should re-organise the structure of this directory. For example we have scripts for deploying in airgap, gathering images from a bundle, and scripts for fetching bundle versions #1035
To quote the PR #1038 (comment)
To Reproduce
Navigate into the
/scripts
dir, wEnvironment
Current main from f54e015
Relevant Log Output
Additional Context
The dir also doesn't contain any README
The text was updated successfully, but these errors were encountered: