BigW Consortium Gitlab
Stop supporting Google Cloud and Azure as backup strategies ## What does this MR do? It removes support for Azure and Google Cloud as backup strategies (via Fog). Motivation behind this decision can be found in !4928, !6713 but basically they require a lot of gems that are unrelated to the backup use-case. ## Are there points in the code the reviewer needs to double check? Am I missing any other location where we'd use these gems? See merge request !7739
Name |
Last commit
|
Last update |
---|---|---|
.. | ||
administration | Loading commit data... | |
api | Loading commit data... | |
ci | Loading commit data... | |
container_registry | Loading commit data... | |
customization | Loading commit data... | |
development | Loading commit data... | |
downgrade_ee_to_ce | Loading commit data... | |
gitlab-basics | Loading commit data... | |
hooks | Loading commit data... | |
incoming_email | Loading commit data... | |
install | Loading commit data... | |
integration | Loading commit data... | |
intro | Loading commit data... | |
legal | Loading commit data... | |
logs | Loading commit data... | |
markdown | Loading commit data... | |
migrate_ci_to_ce | Loading commit data... | |
monitoring | Loading commit data... | |
operations | Loading commit data... | |
permissions | Loading commit data... | |
profile | Loading commit data... | |
project_services | Loading commit data... | |
public_access | Loading commit data... | |
raketasks | Loading commit data... | |
security | Loading commit data... | |
ssh | Loading commit data... | |
system_hooks | Loading commit data... | |
university | Loading commit data... | |
update | Loading commit data... | |
user | Loading commit data... | |
web_hooks | Loading commit data... | |
workflow | Loading commit data... | |
README.md | Loading commit data... |