ThrawnCA

What's the _benefit_ of ditching all the cross-version compatibility?

See https://github.com/ckan/ckanext-xloader/blob/f40d0d0256ca85405a534684e745cb398ed43f9f/ckanext/xloader/plugin.py#L15

Testing indicates that the `package_patch` API and the `resource_patch` API both call the `after_update` function with the full package dictionary, as does editing a resource via the web interface.

Ok, so `resource_patch` and `resource_update` first call `after_update` with the package dict, then with the resource dict. However, the first call generates validation jobs for every resource in the package,...

This is the reason that 4321b79 broke the TravisCI build; as soon as the plugin implemented IPackageController, it started incorrectly generating multiple validation jobs.

@stryx: You could fork it yourself if you like? @Mikaela: There are overheads of running a tool like this (eg extra traffic to probe the HTTPS domain), which Mozilla is...

@adamchainz ec2-metadata looks great, but we're working with a software package (CKAN) that hasn't yet migrated to Python 3.

@zepplen Incidentally, for those needing a workaround, it's very easy with `requests`. Eg to retrieve the equivalent of `get_instance_metadata()['document']`: token = requests.put('http://169.254.169.254/latest/api/token', headers={'X-aws-ec2-metadata-token-ttl-seconds': '60'}).text document = requests.get('http://169.254.169.254/latest/dynamic/instance-identity/document', headers={'X-aws-ec2-metadata-token': token}).json()

At least, it's a bit more work than one request if you want it to be efficient. If you just retrieve a new token every time, you're doubling up all...

Possibly. It depends on exactly where the issue is, but if it's specific to the reports generated by the Maven plugin, then that's probably best.