Skip to content

Commit 53e1ac5

Browse files
committed
tweaks
1 parent 6272517 commit 53e1ac5

2 files changed

Lines changed: 11 additions & 2 deletions

File tree

README.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -43,6 +43,13 @@ mas-devops-create-initial-users
4343
---------------------------------------------
4444

4545

46+
Add to /etc/hosts
47+
```
48+
127.0.0.1 tgk01-masdev.mas-tgk01-manage.svc.cluster.local
49+
127.0.0.1 coreapi.mas-tgk01-core.svc.cluster.local
50+
127.0.0.1 admin-dashboard.mas-tgk01-core.svc.cluster.local
51+
```
52+
4653
```bash
4754
SM_AWS_REGION=""
4855
SM_AWS_ACCESS_KEY_ID=""

src/mas/devops/users.py

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -32,8 +32,11 @@
3232
Perhaps we do the core bits in a core app (suite workspace?)
3333
And app-specific bits in the apps themselves
3434
but if we create a user before manage is ready, sync fails, and no way to trigger resync in MAS < 9.1.0?
35-
3635
# could do it all from a core app, but check for readiness of apps
36+
Run in a dedicated instance-root app in the final syncwave
37+
38+
how ot cope with users that have been soft-deleted? tolerate / skip - ensure they are removed from secret so
39+
we don't get caught in an infinite loop?
3740
3841
'''
3942

@@ -59,7 +62,6 @@ def __init__(self, mas_instance_id: str, mas_workspace_id: str, k8s_client: clie
5962
self.mas_core_namespace = f"mas-{self.mas_instance_id}-core"
6063
self.manage_namespace = f"mas-{self.mas_instance_id}-manage"
6164
self.dyn_client = DynamicClient(self.k8s_client)
62-
self.v1_routes = self.dyn_client.resources.get(api_version="route.openshift.io/v1", kind="Route")
6365
self.v1_secrets = self.dyn_client.resources.get(api_version="v1", kind="Secret")
6466

6567
self._mas_superuser_credentials = None

0 commit comments

Comments
 (0)