| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
| |
AWSTags allows querying tags from EC2, and setting groups based on the
tag names or values.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
The duplicate group check parsed groups differently from the actual
groups.xml parsing routines; the latter followed the documentation,
while the duplicate group check did now. This fixes the duplicate
group check to parse groups.xml correctly when looking for duplicates.
Fixes #140
|
|
|
|
|
|
|
|
|
| |
created
Previously, only two cases were handled properly: both public and
private keys had been created; or neither had been created. If the
private key had been created (e.g., manually added to the repo), the
public key would not be created from it. This fixes that.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Connector plugins can now create new groups, including the full range
of options on those groups (profile, public, category, etc.).
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This monitors XIncluded files even if should_monitor=False, since the
object monitoring the base file will not monitor XIncludes. This
ensures that XIncluded files are properly monitored whenever possible,
particularly for Bundler and Properties.
This is a partial backport of 5b66845 -- as much of a backport as is
possible without a module-level FAM object.
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|
|
|
|
|
| |
This reverts commit 542ededa8297b1889542d97b9bdfb8345dd7550c.
Committed to wrong branch.
|
|
|
|
|
|
| |
This makes HandlesEntry work with the new code that's in place for
StructFile to replace XMLSrc. Fixes
https://github.com/Bcfg2/bcfg2/commit/2169edc1bba82076db776b75db89b79d6f2f4786#commitcomment-3968162
|
|
|
|
|
|
| |
Fixed long lines.
Improved efficiency by avoiding multiple loops over the same data.
|
|
|
|
|
|
|
|
| |
This updates the do_POST() code to cleave more closely to the code in
SimpleXMLRPCHandler.do_POST (plus SSL magic, of course). In doing so,
it eliminates a select() call whose timeouts were not handled
properly, and which thus left stray idle processes around after
incomplete XML-RPC calls.
|
|
|
|
| |
of just self.clients
|
| |
|
|
|
|
|
| |
This makes category negation consistent, and also makes it work like
it did in Bcfg2 1.2
|
|
|
|
|
|
|
|
|
| |
Primarily, this fixes a few potential bugs in initial metadata, which
may result in inconsistent ordering of groups, which can be a problem
when relying on category suppression.
This also deduplicates some category suppression code, and moves some
nested functions to top-level methods, which are surprisingly faster.
|
| |
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|
|
|
|
|
| |
This reverts commit 4f745cc2731f7035f02566ba8bc1a0e9ae1b1a71.
This breaks handling of unicode on python 2.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
This fixes cases where the collection itself would not be cached
because a host had no sources, or multiple sources of different types;
we still want to cache package group results and package sets (both of
which will be empty).
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
| |
|
| |
|
|
|
|
|
| |
Also abstracted getting the list of objects that may register RMI
calls into a separate function.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
This gives a single unified interface for expiring caches, no matter
the plugin. This will be particularly useful with the
MultiprocessingCore, as certain calls must be dispatched to child
processes to expire their caches.
|
| |
|
|\
| |
| |
| |
| | |
fennm/metadata-dont-update-xml-on-gratuitous-profile-update
Metadata: Don't update XML on gratuitous profile update
|
| |
| |
| |
| |
| |
| | |
Rather than doing some ad-hoc lookups of internal data structures
stpierre suggested that it'd be better to use the normal metadata
build procedures. This implements that and adjusts the tests.
|
| |
| |
| |
| |
| |
| | |
Based on the expectations of the tests, I am reasonably confident
that updating the in memory structures is logically part of changing
the client's profile so I put it in the if block
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Check to see if the profile that is being set by set_profile
exactly matches the existing profile list. If it does, then avoid
writing out a new clients.xml. This simple optimization reduces
the amount of clients.xml rewriting that occurs if you have a
bunch of clients running bcfg2 -p at the same time (for example,
during a cluster rebuild).
|
| |
| |
| |
| |
| | |
When reloading probe groups/data for a single client from the
database, only clear data for that client, not for all clients.
|