Support private modules
These should only be accessible whilst logged in - both in the UI and via Terraform.
- Need to work out how authentication via terraform would work.
- Analytics auth tokens would need to become actual auth tokens - should these have global access to all modules (public and private)?
- Who would be able to access modules once logged in? Should they be "public", "internal" and "private"?
- Public - accessible without logging in
- Internal - accessible to any logged in user
- Private - Only accessible when user has namespace access
- Would require a new permission type for namespaces for "read" access
- The user would need to login to obtain a token:
- This could be done via the UI
- Can we utilise terraform login command? Is this only for TFC/TFE?
- How long would the tokens last? Could the user decide?
- For deployment tokens, should a process be created when a deployment environment is provided a static service token and it obtains a temporary terraform auth token during runtime?