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.
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 on the <html> element. For better flexibility, consider using a data-theme attribute instead of a boolean class. This allows each theme to define its own dark/light variants. Additionally, the toggle button should be hidden for mono themes (themes with only one palette). The useDarkMode composable should expose whether the theme is "toggleable", and the navbar should conditionally render the button based on this. Finally, theme configuration should be available in the admin side - the Settings tab in AdminDashboard.vue would be the appropriate place to add theme selection.
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.
Updated some functions to preserve a consistent and deterministic
display order by using OrderedDict.
Adjusted the ordering of entries (and the content) 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.
Applied to WindRiver.
Request authenticated through IRC + DevCentral commit + prior knowledge of upcoming commit irl + familiar pattern of activity.
"Past Incidents" section in StatusPage.vue shows 5 most recent. Add a "View all" link to /incidents when incidents are more than 5.
NEW BRANCH D3983
NEW BRANCH D3983
NEW COMMIT D3983
COCNTINUE
Added 1 blank line
I added a test to determine if the function get_carp_entries() will avoid an FHRP group
if it's not the CARP protocol. Also, it is more readable if we place the CARP configuration directly in the forest.yaml.
testing arc diff
Removed unused imports
Added README.md file for installation steps
Added Nasqueron header in the plugin file
@yousra I think pip install salt==3006.8 should work, with dependencies.
Caught this issue during dependencies test.
Salt dependencies are reasonable enough to add to requirements.txt:
Plugin works, but we need more metadata:
If Salt dependencies are the issue, a possibility is to define requirements from https://github.com/saltstack/salt/tree/master/requirements