#9908 Access to the status.fedoraproject.org page
Closed: Fixed 2 years ago by kevin. Opened 2 years ago by frostyx.

Describe what you would like us to do:

Can you please grant me access to modify https://status.fedoraproject.org ?
As a Copr maintainer, I work on new releases, server upgrades, and other administrative tasks (tomorrow we are doing #9894). I would like to have the option to update the copr badge on the status page.

Per SOP - https://fedora-infra-docs.readthedocs.io/en/latest/sysadmin-guide/sops/status-fedora.html - I need following:

Only members of sysadmin-main and people given the AWS credentials can update the status website. Additionally, you also need to have commit access to “statusfpo” git repository on GitHub - one way to get it is becoming member of “noc” team at “fedora-infra” organization.

When do you need this to be done by? (YYYY/MM/DD)

At your convenience, no deadline.


Metadata Update from @kevin:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: low-gain, low-trouble, ops

2 years ago

email sent to requester about getting aws keys

Anything else that needs to be done?

I'm going to close this, re-open if there's anything further to do.

Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

2 years ago

Thank you, I can't believe it is six months already.

@mobrien sent me email regarding AWS keys and I managed to successfully configure them.

[jkadlcik statusfpo]$ make upload        
pelican /home/jkadlcik/git/statusfpo/content -o /home/jkadlcik/git/statusfpo/output -s /home/jkadlcik/git/statusfpo/publishconf.py 
Done: Processed 96 articles, 0 drafts, 0 pages, 0 hidden pages and 0 draft pages in 0.83 seconds.
aws --profile statusfpo s3 cp /home/jkadlcik/git/statusfpo/output/ s3://status.fedoraproject.org/ --recursive --exclude "theme/*"
upload: output/index.html to s3://status.fedoraproject.org/index.html
upload: output/planned.rss to s3://status.fedoraproject.org/planned.rss
upload: output/changes.rss to s3://status.fedoraproject.org/changes.rss
upload: output/resolved.rss to s3://status.fedoraproject.org/resolved.rss
upload: output/resolved.html to s3://status.fedoraproject.org/resolved.html
aws --profile statusfpo cloudfront create-invalidation --distribution-id E2ROJ0IZ3EJ66H --paths /index.html /resolved.html /changes.rss /ongoing.rss /planned.rss /resolved.rss
{
    "Location": "https://cloudfront.amazonaws.com/2020-05-31/distribution/E2ROJ0IZ3EJ66H/invalidation/I1CFIMDKQ2MOBB",
    "Invalidation": {     
        "Id": "I1CFIMDKQ2MOBB",
        "Status": "InProgress",
        "CreateTime": "2021-11-10T15:58:44.939Z",
        "InvalidationBatch": {
            "Paths": {
                "Quantity": 6,
                "Items": [
                    "/changes.rss",
                    "/ongoing.rss",
                    "/resolved.rss",
                    "/resolved.html",
                    "/index.html",
                    "/planned.rss"
                ]
            },
            "CallerReference": "cli-1636559924-264226"
        }
    }
}

The problem is, that I probably don't have the correct rights for
https://github.com/fedora-infra/statusfpo

I was able to clone it with git clone git@github.com:fedora-infra/statusfpo.git but I cannot push

[jkadlcik@sagemcom statusfpo]$ git push
ERROR: Permission to fedora-infra/statusfpo.git denied to FrostyX.
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

My apologies if the problem is on my side

Metadata Update from @frostyx:
- Issue status updated to: Open (was: Closed)

2 years ago

Can you tell us the github id's of the people in the copr team who should have access?

@kevin sure, sorry, it didn't occur to me.

Added you both!

Let me know if there's anything more that needs doing. :)

Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

2 years ago

Thank you very much, I am confirming that git push now works.
PS: I needed to set up 2FA for my GitHub account, in case anyone else wonders why they cannot push.

Login to comment on this ticket.

Metadata
Boards 1
ops Status: Done