Helper method for creating cloud configs
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Idoneità per principianti
- 25/100
Direzione di ricerca
Start by reviewing the existing CLI entry points and the current cloud configuration handling. Define the scope for interactive cloudconfig creation, subscription versus order syntax, and environment-variable support before implementation. Done should include an agreed command design that creates usable configuration without requiring users to write JSON.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Right now we make users just specify a json file for their cloud configuration.
It'd be great if we could help them a bit, with a CLI to more easily create a cloudconfig json without having to think about JSON.
Most people will likely just create one or at most a handful of these, and likely store them somewhere they could easily access them. So we could try to do a more interactive approach, where they enter the cloud they want to configure for, and then it asks them the questions, perhaps with pointers on how to get the info.
That could also open the possibility to try to do more streamlined things, like if there are ways to integrate with the cloud CLI's and extract the auth from them or make calls on the user's behalf.
Right now orders and subscriptions are basically the same, but have slightly different syntaxes, just like in #601. So a top level planet cloudconfig option likely makes sense. It sounds like the Planet API team is up for orders to support the subscriptions syntax before too long, so we could default to subscription style, but have an alternate --order option that would make it in the order style to be used before the API accepts both.
Could be nice to be able to set cloudconfig as an environmental variable, so you don't have to keep referring to it. Or some other mechanism to just set it and use it, and maybe easily change to one of a handful of options.
- Lingua principale
- Python
- Stelle
- 299
- Fork
- 100
- Merge medio
- 7g 8h
- PR unite (30g)
- 2
Guida per i contributori
Apri la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di planetlabs/planet-client-python
-
better-testing
Difficoltà 2/5 1-3 ore Idoneità per principianti 65/100
planetlabs/planet-client-python#1110 ·
-
proposal
Difficoltà 3/5 1-2 giorni Idoneità per principianti 65/100
planetlabs/planet-client-python#1221 ·
-
proposal
Difficoltà 3/5 1-2 giorni Idoneità per principianti 57/100
planetlabs/planet-client-python#1214 ·
-
bug
Difficoltà 3/5 1-2 giorni Idoneità per principianti 48/100
planetlabs/planet-client-python#1197 · 1 commento · 1 reazione ·
-
Quota API Apertaai-claude
planetlabs/planet-client-python#1191 · 1 commento · 1 assegnatario ·
Tutte le issue di planetlabs/planet-client-python
Issue simili
-
triage/confirmed
Difficoltà 2/5 1-3 ore Idoneità per principianti 88/100
agentscope-ai/agentscope#2775 ·
-
comp/desktop P3 type/bug
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 92/100
NousResearch/hermes-agent#118866 ·
-
bug
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 90/100
apache/cloudstack#14222 ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100