cms-dev / cms-dev/cms

Follow up to administrative accounts

Open
#521 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
1k
Forks
412
Avg merge
6d 10h
Merged PRs (30d)
3

Description

Quoting @giomasce:

I personally would prefer a configuration option, because usually either you want AWS admins or you don't. It is not something you may want to change often between two runs of the same installation.

Another thing that has to be fixed is the user documentation, particularly with respect to the part where we say that AWS has to be protected because it has no login.
Also documentation can go in another PR. Please open issues to remind us of missing docs and login disabling option.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the quoted discussion about AWS administrative accounts, login disabling, and the existing user documentation. Clarify whether the intended work is a configuration option, documentation updates, or separate issues; done should be defined before implementation because no files, tests, or entry points are named.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
authentication, cloud, documentation
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.