[FEATURE] Introduce --temporary-external-ip flag for deploy command
- Dominant language
- Python
- Stars
- 3
- Forks
- 4
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 11
Description
### Summary
Introduce --temporary-external-ip flag for deploy command
### Motivation
Introduce --temporary-external-ip flag for deploy command, so that users don't have to remove the IP after, but that is needed for some of the items to deploy the first time you are not in the same network
### Proposed Implementation
_No response_
### Alternatives Considered
_No response_
### Priority
None
Contributor guide
Research direction
Start by locating the deploy command and its existing external-IP handling. Read the deploy entry point and any related tests to understand how first-time deployments work when the user is outside the network. Done means the new --temporary-external-ip flag is accepted by deploy and the described remote first deployment no longer requires manual IP removal afterward.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100