@Duranzed As a follow-up for the Terminator plugin, that one could be interesting too.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Yesterday
Plugin works, but now we need to polish the two README files.
Configuration logic. Looks good to me.
Service part OK.
Per https://cbea.ms/git-commit/ titles of your commit messages should be much shorter.
Fixed the remaining issues (tailwind config, useDarkMode with data-theme, stray Z in test)
Tue, Mar 3
Add some changes : some flags where missing
Add canonical_public_ipv4 for Ysul
No link to a task in description?
OK for Wolfplex too.
In D3989#61933, @Chenani-MohamedAmine wrote:"Ref T2246"
Change the files motd for db-a-001 and db-b-001
- Added "View all" link in StatusPage when resolved incidents > 5
- Changed created_at to start_date in test mock data
- Moved IncidentHistory.test.js to views/__tests__/
- Added error logging in getById catch handler
- Added an init.sls pour strongswan
rename db-B-001 to db-b-001 across the repository
This change touches Wolfplex files. As such, administrative approval is needed from Wolfplex technical contact.
Standardize NTP configuration (T1223) - v2
Remove accidental file t
resolved here
Ref T1695
Rename network interfaces on selected machines to standardize the naming convention across all hosts, using intranought and public.
The implementation uses a boolean dark class. Since tools have many themes these days and flexibility is important, consider implementing this as a theme-based system instead of binary dark/light. This would allow adding more themes in the future (e.g., high contrast, brand themes) without architectural changes.
I just noticed that IncidentHistory.test.js tests a view but is in components/__tests__/.
Move the file to views/__tests__/ for consistency.
In D3980#61784, @ieli wrote:"Past Incidents" section in StatusPage.vue shows 5 most recent. Add a "View all" link to /incidents when incidents are more than 5.
Mon, Mar 2
Updated some functions to preserve a consistent and deterministic
display order by using OrderedDict.
Adjusted the ordering of entries in nodes.sls to maintain consistency with the generated pillar structure and ensure deterministic output.
I tried pip install salt==3006.8, but it brings the same strange issue : AttributeError: cannot access submodule 'cmdmod' of module 'salt.modules' (most likely due to a circular import)
(same in WindRiver)
$ sudo salt complector state.sls_id salt-node-cloudhugger roles/vault/policies test=True complector: ---------- ID: salt-node-cloudhugger Function: vault.policy_present Result: None Comment: Policy would be changed Started: 18:09:21.668208 Duration: 841.275 ms Changes: ---------- salt-node-cloudhugger: ---------- change: --- +++ @@ -10,3 +10,7 @@ path "ops/data/secrets/nasqueron/opensearch/infra-logs/internal_users/dashboards" { capabilities = [ "read" ] } + +path "ops/data/secrets/network/ipsec/key" { + capabilities = [ "read" ] +}
Using a separate file like /etc/rc.conf.d/netif/carp keeps the CARP configuration isolated,
avoids modifying the main /etc/rc.conf, and makes the setup cleaner and safer.
It improves maintainability, reduces the risk of conflicts, and ensures a more modular infrastructure design.
- Added component tests (IncidentHistory.test.js)
- Updated docs/architecture.md with IncidentHistory.vue in diagram