cloud-native-toolkit / cloud-native-toolkit/software-everywhere
destroy on generated automation packages are not removing components from github repo
Open
bug
type:gitops
- Dominant language
- TypeScript
- Stars
- 8
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
when issuing a destroy after a successful install using our generated automation from a BOM (so any of the automation on github.com/ibm automation solutions) the destroy leaves the generated components within the github deploy repo, these have to manually be removed for a subsequent install using the same repo which is really tedious and can be complex for a user.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.